Hi Brad,
The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC. If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version. So it sounds like your USB connection is not even physically present to get that behavior. But yet something appears in device manager?
Regards
TK
| Group: DynoMotion |
Message: 4768 |
From: bradodarb |
Date: 5/4/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
I have tried every USB port on this box and it is all the same.
I plugged it into my dev laptop and it still works, so kflop is good.
Incidentally, I have several working USB devices on this machine
(mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
Maybe a win8 bug?
-Brad Murry
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Brad,
> Â
> The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC. If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version. So it sounds like your USB connection is not even physically present to get that behavior. But yet something appears in device manager?
> Â
> Regards
> TK
> Â
> Â
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Friday, May 4, 2012 10:30 AM
> Subject: [DynoMotion] AMD 64 on a 32 bit OS
>
>
> Â
> So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
>
> I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
>
> I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
>
> I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
>
> I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
>
> Thanks,
> -Brad Murry
> |
|
| Group: DynoMotion |
Message: 4769 |
From: bradodarb |
Date: 5/4/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
In case anyone is interested in trying this or did not know there was a win8 preview-
http://windows.microsoft.com/en-US/windows-8/download
I can say that win 8 is amazing so far. from deep hibernate to actually ready to work is less than 4 seconds.
Oh well, at least we can get a head start on supporting 8!
-Brad Murry
--- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@...> wrote:
>
> I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
>
> I have tried every USB port on this box and it is all the same.
>
> I plugged it into my dev laptop and it still works, so kflop is good.
>
> Incidentally, I have several working USB devices on this machine
> (mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
>
> Maybe a win8 bug?
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Brad,
> > Â
> > The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC. If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version. So it sounds like your USB connection is not even physically present to get that behavior. But yet something appears in device manager?
> > Â
> > Regards
> > TK
> > Â
> > Â
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Friday, May 4, 2012 10:30 AM
> > Subject: [DynoMotion] AMD 64 on a 32 bit OS
> >
> >
> > Â
> > So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
> >
> > I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
> >
> > I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
> >
> > I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
> >
> > I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
> >
> > Thanks,
> > -Brad Murry
> >
> |
|
| Group: DynoMotion |
Message: 4770 |
From: Kyryl Perederiy |
Date: 5/4/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Brad,
Have you tried the latest FTDI driver yet? It does not list Win8 as a
supported platform, but chances are it may work.
-Kyryl
Sent: Friday, May 04, 2012 12:01 PM
Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
In case anyone is interested in trying this or did not know there was a win8
preview-
http://windows.microsoft.com/en-US/windows-8/download
I
can say that win 8 is amazing so far. from deep hibernate to actually ready to
work is less than 4 seconds.
Oh well, at least we can get a head start on
supporting 8!
-Brad Murry
--- In mailto:DynoMotion%40yahoogroups.com,
"bradodarb" <bradodarb@...> wrote:
>
> I verified it is in the
Device Manager under [Other Devices] listed as ! Unknown device >
>
I have tried every USB port on this box and it is all the same. >
>
I plugged it into my dev laptop and it still works, so kflop is good. >
> Incidentally, I have several working USB devices on this
machine > (mouse, keyboard, webcam, Skype headset and I have also been
able to USB connect to several other micro-controllers with no probs. >
> Maybe a win8 bug?
>
> -Brad Murry
>
> --- In
mailto:DynoMotion%40yahoogroups.com,
Tom Kerekes <tk@> wrote: > >
> > Hi Brad,
> > Â
> > The 3 seconds of rapid blinking that KFLOP normally does is
performed by the bootloader to check if a Flash recovery is being requested by
the PC. If KFLOP determines that there is no PC connection (by checking
the +5V line on the USB connector) it skips that and jumps immediately into the
Firmware Version. So it sounds like your USB connection is not even
physically present to get that behavior. But yet something appears in
device manager? > > Â
> > Regards
> > TK
>
> Â
> > Â
> >
> > From: bradodarb
<bradodarb@> > > To: href="mailto:DynoMotion%40yahoogroups.com">mailto:DynoMotion%40yahoogroups.com
> > Sent: Friday, May 4, 2012 10:30 AM
> > Subject:
[DynoMotion] AMD 64 on a 32 bit OS > >
> >
> >
 > > So I re-commissioned a ~3 year old optiplex740 with an
AMD64bit proc. > >
> > I am running Windows8 32 bit because
the 64bit version did not support drivers for my NVidia Quattro. > >
> > I was able to install KMotion4.29 with no real issues, but when I
plug in my kflop, I don't get the normal blinking pattern, just a quick single
pulse and then both on solid. > >
> > I also cannot seem to
install the FTDI driver. It just shows up as unknown device in the device
manager and when I try to manually install the driver it states there is no
suitable driver found. > >
> > I know Win8 is not supported
yet by Dyno, but I'm hoping someone can offer some suggestions. > >
> > Thanks,
> > -Brad Murry
>
>
>
|
|
| Group: DynoMotion |
Message: 4771 |
From: bradodarb |
Date: 5/4/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Thanks Kyryl,
I just installed that driver as well, and no dice I'm afraid.
When I plug the kflop in, I get a notification in my system tray stating that the usb device malfunctioned and widows was unable to recognize it....
Still works on Win7
-Brad Murry
--- In DynoMotion@yahoogroups.com, "Kyryl Perederiy" <kyrylo@...> wrote:
>
> Brad,
>
> Have you tried the latest FTDI driver yet? It does not list Win8 as a supported platform, but chances are it may work.
> http://www.ftdichip.com/Drivers/VCP.htm
>
> -Kyryl
>
> From: bradodarb
> Sent: Friday, May 04, 2012 12:01 PM
> To: DynoMotion@yahoogroups.com
> Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
>
>
> In case anyone is interested in trying this or did not know there was a win8 preview-
>
> http://windows.microsoft.com/en-US/windows-8/download
>
> I can say that win 8 is amazing so far. from deep hibernate to actually ready to work is less than 4 seconds.
>
> Oh well, at least we can get a head start on supporting 8!
>
> -Brad Murry
>
> --- In mailto:DynoMotion%40yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> >
> > I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
> >
> > I have tried every USB port on this box and it is all the same.
> >
> > I plugged it into my dev laptop and it still works, so kflop is good.
> >
> > Incidentally, I have several working USB devices on this machine
> > (mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
> >
> > Maybe a win8 bug?
> >
> > -Brad Murry
> >
> > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Brad,
> > > Ã
> > > The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC.Ã If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version.Ã So it sounds like your USB connection is not even physically present to get that behavior.Ã But yet something appears in device manager?
> > > Ã
> > > Regards
> > > TK
> > > Ã
> > > Ã
> > >
> > > From: bradodarb <bradodarb@>
> > > To: mailto:DynoMotion%40yahoogroups.com
> > > Sent: Friday, May 4, 2012 10:30 AM
> > > Subject: [DynoMotion] AMD 64 on a 32 bit OS
> > >
> > >
> > > Ã
> > > So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
> > >
> > > I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
> > >
> > > I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
> > >
> > > I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
> > >
> > > I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
> > >
> > > Thanks,
> > > -Brad Murry
> > >
> >
> |
|
| Group: DynoMotion |
Message: 4772 |
From: Tom Kerekes |
Date: 5/4/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Hi Brad,
I'm not sure how deep you want to get into this but W7 (and I assume W8) includes Microsoft Certified Drivers for the FT245RL USB chip that we use. However we change the VID and PID to be unique to KFLOP so it can be identified as a KFLOP and not something else with the same FTDI chip. So Windows thinks the device is incompatible. There is a utility from FTDI that can be used to erase our Configuration so it will then load the standard Windows supplied drivers. You might try that just to see if the device then installs properly
into device manager as an FTDI device. Our libraries only open FTDI devices that contain the word "KFLOP" or "KMotion" or "Dynomotion" in the driver name so if you do this our Libraries will not recognize the device as a KFLOP. You might be able to re-name the driver using Device Manager. Otherwise you could modify our KMotionDLL library to attach to any FTDI device by removing the name restriction. It's easy to re-flash our configuration into the FTDI chip. I'll attach the required XML file in case you don't have it. I wonder if Microsoft in their infinite wisdom now refuses to load non-certified device drivers in W8?
Regards
TK
| Group: DynoMotion |
Message: 4773 |
From: Tom Kerekes |
Date: 5/4/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Opps forgot the link to the FT_PROG Utility
TK
| Group: DynoMotion |
Message: 4774 |
From: bradodarb |
Date: 5/4/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Hello Tom,
I'd love to get it working as this box will become my primary dev machine for this kind of stuff and I am really loving Win8.
So, I'm down to go deep as long as there is a reasonable amount of guidance.
I looked at the link and noticed many tools, can you specify the correct one?
If the ID's are the problem. I reckon a new device discovery scheme will need to be thought about so as not to corrupt the expected VID/PID.
If that is not the issue, I will need to get at that XML.
Thanks,
-Brad Murry
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Opps forgot the link to the FT_PROG Utility
> Â
> http://www.ftdichip.com/Support/Utilities.htm
> Â
> TK
>
> From: Tom Kerekes <tk@...>
> To: "DynoMotion@yahoogroups.com" <DynoMotion@yahoogroups.com>
> Sent: Friday, May 4, 2012 1:58 PM
> Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
>
>
> Hi Brad,
> Â
> I'm not sure how deep you want to get into this but W7 (and I assume W8) includes Microsoft Certified Drivers for the FT245RL USB chip that we use. However we change the VID and PID to be unique to KFLOP so it can be identified as a KFLOP and not something else with the same FTDI chip. So Windows thinks the device is incompatible. There is a utility from FTDI that can be used to erase our Configuration so it will then load the standard Windows supplied drivers.  You might try that just to see if the device then installs properly into device manager as an FTDI device. Our libraries only open FTDI devices that contain the word "KFLOP" or "KMotion" or "Dynomotion" in the driver name so if you do this our Libraries will not recognize the device as a KFLOP. You might be able to re-name the driver using Device Manager. Otherwise you could modify our KMotionDLL library to attach to any FTDI device by removing the name restriction.  It's easy
> to re-flash our configuration into the FTDI chip. I'll attach the required XML file in case you don't have it. I wonder if Microsoft in their infinite wisdom now refuses to load non-certified device drivers in W8?
> Â
> Regards
> TK
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Friday, May 4, 2012 1:36 PM
> Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
>
>
> Â
>
> Thanks Kyryl,
>
> I just installed that driver as well, and no dice I'm afraid.
>
> When I plug the kflop in, I get a notification in my system tray stating that the usb device malfunctioned and widows was unable to recognize it....
>
> Still works on Win7
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> >
> > Brad,
> >
> > Have you tried the latest FTDI driver yet? It does not list Win8 as a supported platform, but chances are it may work.
> > http://www.ftdichip.com/Drivers/VCP.htm
> >
> > -Kyryl
> >
> > From: bradodarb
> > Sent: Friday, May 04, 2012 12:01 PM
> > To: DynoMotion@yahoogroups.com
> > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> >
> >
> > In case anyone is interested in trying this or did not know there was a win8 preview-
> >
> > http://windows.microsoft.com/en-US/windows-8/download
> >
> > I can say that win 8 is amazing so far. from deep hibernate to actually ready to work is less than 4 seconds.
> >
> > Oh well, at least we can get a head start on supporting 8!
> >
> > -Brad Murry
> >
> > --- In mailto:DynoMotion%40yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > >
> > > I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
> > >
> > > I have tried every USB port on this box and it is all the same.
> > >
> > > I plugged it into my dev laptop and it still works, so kflop is good.
> > >
> > > Incidentally, I have several working USB devices on this machine
> > > (mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
> > >
> > > Maybe a win8 bug?
> > >
> > > -Brad Murry
> > >
> > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Brad,
> > > > Ãâ
> > > > The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC.Ãâ If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version.Ãâ So it sounds like your USB connection is not even physically present to get that behavior.Ãâ But yet something appears in device manager?
> > > > Ãâ
> > > > Regards
> > > > TK
> > > > Ãâ
> > > > Ãâ
> > > >
> > > > From: bradodarb <bradodarb@>
> > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > Sent: Friday, May 4, 2012 10:30 AM
> > > > Subject: [DynoMotion] AMD 64 on a 32 bit OS
> > > >
> > > >
> > > > Ãâ
> > > > So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
> > > >
> > > > I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
> > > >
> > > > I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
> > > >
> > > > I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
> > > >
> > > > I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
> > > >
> > > > Thanks,
> > > > -Brad Murry
> > > >
> > >
> >
> |
|
| Group: DynoMotion |
Message: 4775 |
From: Tom Kerekes |
Date: 5/4/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
It is the: FT_PROG 2.6.8 - EEPROM Programming Utility
TK
| Group: DynoMotion |
Message: 4776 |
From: Kyryl Perederiy |
Date: 5/4/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
As an alternative I would try to disable Driver Signature Enforcement. You
will need to enable Safe Mode to do that. Google "Disable Signature Enforcement"
"Windows 8".
-Kyryl
Sent: Friday, May 04, 2012 2:37 PM
Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit
OS
It is the: FT_PROG 2.6.8 - EEPROM
Programming Utility
TK
| Group: DynoMotion |
Message: 4777 |
From: bradodarb |
Date: 5/4/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Kyryl,
You are the man!
After a few cycles of downloading the utility from FTDI and running into several dll not found errors- prompting me to try reinstalling the drivers....
I received your suggestion and I am now connected to my Kflop inside win8!
The actual procedure was simple enough::
1) open msconfig
2) check safe mode from boot tab
3) restart
4) plug in Kflop
5) go to device manager
6) update driver
7) open msconfig
8) reset boot options to the original state
9) restart
10) enjoy kflop on windows 8( and with new kflop web+websocket server create CNC metro app!)
Thanks Kyryl for the painless suggestion and Tom for the useful and interesting links.
-Brad Murry
Sent from my Windows 8 PC
--- In DynoMotion@yahoogroups.com, "Kyryl Perederiy" <kyrylo@...> wrote:
>
> As an alternative I would try to disable Driver Signature Enforcement. You will need to enable Safe Mode to do that. Google "Disable Signature Enforcement" "Windows 8".
>
> -Kyryl
>
> From: Tom Kerekes
> Sent: Friday, May 04, 2012 2:37 PM
> To: DynoMotion@yahoogroups.com
> Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
>
>
>
> It is the: FT_PROG 2.6.8 - EEPROM Programming Utility
>
> TK
>
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Friday, May 4, 2012 2:24 PM
> Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
>
>
>
> Hello Tom,
>
> I'd love to get it working as this box will become my primary dev machine for this kind of stuff and I am really loving Win8.
>
> So, I'm down to go deep as long as there is a reasonable amount of guidance.
>
> I looked at the link and noticed many tools, can you specify the correct one?
>
> If the ID's are the problem. I reckon a new device discovery scheme will need to be thought about so as not to corrupt the expected VID/PID.
>
> If that is not the issue, I will need to get at that XML.
>
> Thanks,
>
> -Brad Murry
>
> --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Opps forgot the link to the FT_PROG Utility
> > Ã
> > http://www.ftdichip.com/Support/Utilities.htm
> > Ã
> > TK
> >
> > From: Tom Kerekes <tk@>
> > To: "mailto:DynoMotion%40yahoogroups.com" <mailto:DynoMotion%40yahoogroups.com>
> > Sent: Friday, May 4, 2012 1:58 PM
> > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> >
> >
> > Hi Brad,
> > Ã
> > I'm not sure how deep you want to get into this but W7 (and I assume W8) includes Microsoft Certified Drivers for the FT245RL USB chip that we use.à However we change the VID and PID to be unique to KFLOP so it can be identified as a KFLOP and not something else with the same FTDI chip.à So Windows thinks the device is incompatible.à There is a utility from FTDI that can be used to erase our Configuration so it will then load the standard Windows supplied drivers.à à You might try that just to see if the device then installs properly into device manager as an FTDI device.à Our libraries only open FTDI devices that contain the word "KFLOP" or "KMotion" or "Dynomotion"à in the driver name so if you do this our Libraries will not recognize the device as a KFLOP.à You might be able to re-name the driver using Device Manager.à Otherwise you could modifyà our KMotionDLL library to attach to any FTDI device by removing the name restriction.à à It's easy
> > to re-flash our configuration into the FTDI chip.Ã I'll attach the required XML file in case you don't have it.Ã I wonder if Microsoft in their infinite wisdom now refuses to load non-certified device drivers in W8?
> > Ã
> > Regards
> > TK
> >
> > From: bradodarb <bradodarb@>
> > To: mailto:DynoMotion%40yahoogroups.com
> > Sent: Friday, May 4, 2012 1:36 PM
> > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> >
> >
> > Ã
> >
> > Thanks Kyryl,
> >
> > I just installed that driver as well, and no dice I'm afraid.
> >
> > When I plug the kflop in, I get a notification in my system tray stating that the usb device malfunctioned and widows was unable to recognize it....
> >
> > Still works on Win7
> >
> > -Brad Murry
> >
> > --- In mailto:DynoMotion%40yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > >
> > > Brad,
> > >
> > > Have you tried the latest FTDI driver yet? It does not list Win8 as a supported platform, but chances are it may work.
> > > http://www.ftdichip.com/Drivers/VCP.htm
> > >
> > > -Kyryl
> > >
> > > From: bradodarb
> > > Sent: Friday, May 04, 2012 12:01 PM
> > > To: mailto:DynoMotion%40yahoogroups.com
> > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > >
> > >
> > > In case anyone is interested in trying this or did not know there was a win8 preview-
> > >
> > > http://windows.microsoft.com/en-US/windows-8/download
> > >
> > > I can say that win 8 is amazing so far. from deep hibernate to actually ready to work is less than 4 seconds.
> > >
> > > Oh well, at least we can get a head start on supporting 8!
> > >
> > > -Brad Murry
> > >
> > > --- In mailto:DynoMotion%40yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > > >
> > > > I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
> > > >
> > > > I have tried every USB port on this box and it is all the same.
> > > >
> > > > I plugged it into my dev laptop and it still works, so kflop is good.
> > > >
> > > > Incidentally, I have several working USB devices on this machine
> > > > (mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
> > > >
> > > > Maybe a win8 bug?
> > > >
> > > > -Brad Murry
> > > >
> > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Brad,
> > > > > ÃÆ'ââ¬Å¡
> > > > > The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC.ÃÆ'ââ¬Å¡ If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version.ÃÆ'ââ¬Å¡ So it sounds like your USB connection is not even physically present to get that behavior.ÃÆ'ââ¬Å¡ But yet something appears in device manager?
> > > > > ÃÆ'ââ¬Å¡
> > > > > Regards
> > > > > TK
> > > > > ÃÆ'ââ¬Å¡
> > > > > ÃÆ'ââ¬Å¡
> > > > >
> > > > > From: bradodarb <bradodarb@>
> > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > Sent: Friday, May 4, 2012 10:30 AM
> > > > > Subject: [DynoMotion] AMD 64 on a 32 bit OS
> > > > >
> > > > >
> > > > > ÃÆ'ââ¬Å¡
> > > > > So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
> > > > >
> > > > > I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
> > > > >
> > > > > I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
> > > > >
> > > > > I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
> > > > >
> > > > > I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
> > > > >
> > > > > Thanks,
> > > > > -Brad Murry
> > > > >
> > > >
> > >
> >
> |
|
| Group: DynoMotion |
Message: 4840 |
From: bradodarb |
Date: 5/8/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Update::
It seems the steps listed do yield a usable system... UNITL you disconnect the Kflop.
I may have to look again at those utilities to find a more permanent solution.
Tom - how would you like to see this happen to get ready for win8?
-Brad
--- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@...> wrote:
>
>
>
> Kyryl,
>
>
>
> You are the man!
>
>
>
> After a few cycles of downloading the utility from FTDI and running into several dll not found errors- prompting me to try reinstalling the drivers....
>
>
>
> I received your suggestion and I am now connected to my Kflop inside win8!
>
>
>
> The actual procedure was simple enough::
>
>
>
> 1) open msconfig
>
> 2) check safe mode from boot tab
>
> 3) restart
>
> 4) plug in Kflop
>
> 5) go to device manager
>
> 6) update driver
>
> 7) open msconfig
>
> 8) reset boot options to the original state
>
> 9) restart
>
> 10) enjoy kflop on windows 8( and with new kflop web+websocket server create CNC metro app!)
>
>
>
>
>
> Thanks Kyryl for the painless suggestion and Tom for the useful and interesting links.
>
>
>
> -Brad Murry
>
>
>
> Sent from my Windows 8 PC
> --- In DynoMotion@yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> >
> > As an alternative I would try to disable Driver Signature Enforcement. You will need to enable Safe Mode to do that. Google "Disable Signature Enforcement" "Windows 8".
> >
> > -Kyryl
> >
> > From: Tom Kerekes
> > Sent: Friday, May 04, 2012 2:37 PM
> > To: DynoMotion@yahoogroups.com
> > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> >
> >
> >
> > It is the: FT_PROG 2.6.8 - EEPROM Programming Utility
> >
> > TK
> >
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Friday, May 4, 2012 2:24 PM
> > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> >
> >
> >
> > Hello Tom,
> >
> > I'd love to get it working as this box will become my primary dev machine for this kind of stuff and I am really loving Win8.
> >
> > So, I'm down to go deep as long as there is a reasonable amount of guidance.
> >
> > I looked at the link and noticed many tools, can you specify the correct one?
> >
> > If the ID's are the problem. I reckon a new device discovery scheme will need to be thought about so as not to corrupt the expected VID/PID.
> >
> > If that is not the issue, I will need to get at that XML.
> >
> > Thanks,
> >
> > -Brad Murry
> >
> > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Opps forgot the link to the FT_PROG Utility
> > > Ã
> > > http://www.ftdichip.com/Support/Utilities.htm
> > > Ã
> > > TK
> > >
> > > From: Tom Kerekes <tk@>
> > > To: "mailto:DynoMotion%40yahoogroups.com" <mailto:DynoMotion%40yahoogroups.com>
> > > Sent: Friday, May 4, 2012 1:58 PM
> > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > >
> > >
> > > Hi Brad,
> > > Ã
> > > I'm not sure how deep you want to get into this but W7 (and I assume W8) includes Microsoft Certified Drivers for the FT245RL USB chip that we use.à However we change the VID and PID to be unique to KFLOP so it can be identified as a KFLOP and not something else with the same FTDI chip.à So Windows thinks the device is incompatible.à There is a utility from FTDI that can be used to erase our Configuration so it will then load the standard Windows supplied drivers.à à You might try that just to see if the device then installs properly into device manager as an FTDI device.à Our libraries only open FTDI devices that contain the word "KFLOP" or "KMotion" or "Dynomotion"à in the driver name so if you do this our Libraries will not recognize the device as a KFLOP.à You might be able to re-name the driver using Device Manager.à Otherwise you could modifyà our KMotionDLL library to attach to any FTDI device by removing the name restriction.à à It's easy
> > > to re-flash our configuration into the FTDI chip.Ã I'll attach the required XML file in case you don't have it.Ã I wonder if Microsoft in their infinite wisdom now refuses to load non-certified device drivers in W8?
> > > Ã
> > > Regards
> > > TK
> > >
> > > From: bradodarb <bradodarb@>
> > > To: mailto:DynoMotion%40yahoogroups.com
> > > Sent: Friday, May 4, 2012 1:36 PM
> > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > >
> > >
> > > Ã
> > >
> > > Thanks Kyryl,
> > >
> > > I just installed that driver as well, and no dice I'm afraid.
> > >
> > > When I plug the kflop in, I get a notification in my system tray stating that the usb device malfunctioned and widows was unable to recognize it....
> > >
> > > Still works on Win7
> > >
> > > -Brad Murry
> > >
> > > --- In mailto:DynoMotion%40yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > > >
> > > > Brad,
> > > >
> > > > Have you tried the latest FTDI driver yet? It does not list Win8 as a supported platform, but chances are it may work.
> > > > http://www.ftdichip.com/Drivers/VCP.htm
> > > >
> > > > -Kyryl
> > > >
> > > > From: bradodarb
> > > > Sent: Friday, May 04, 2012 12:01 PM
> > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > >
> > > >
> > > > In case anyone is interested in trying this or did not know there was a win8 preview-
> > > >
> > > > http://windows.microsoft.com/en-US/windows-8/download
> > > >
> > > > I can say that win 8 is amazing so far. from deep hibernate to actually ready to work is less than 4 seconds.
> > > >
> > > > Oh well, at least we can get a head start on supporting 8!
> > > >
> > > > -Brad Murry
> > > >
> > > > --- In mailto:DynoMotion%40yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > > > >
> > > > > I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
> > > > >
> > > > > I have tried every USB port on this box and it is all the same.
> > > > >
> > > > > I plugged it into my dev laptop and it still works, so kflop is good.
> > > > >
> > > > > Incidentally, I have several working USB devices on this machine
> > > > > (mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
> > > > >
> > > > > Maybe a win8 bug?
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > >
> > > > > > Hi Brad,
> > > > > > ÃÆ'ââ¬Å¡
> > > > > > The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC.ÃÆ'ââ¬Å¡ If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version.ÃÆ'ââ¬Å¡ So it sounds like your USB connection is not even physically present to get that behavior.ÃÆ'ââ¬Å¡ But yet something appears in device manager?
> > > > > > ÃÆ'ââ¬Å¡
> > > > > > Regards
> > > > > > TK
> > > > > > ÃÆ'ââ¬Å¡
> > > > > > ÃÆ'ââ¬Å¡
> > > > > >
> > > > > > From: bradodarb <bradodarb@>
> > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > Sent: Friday, May 4, 2012 10:30 AM
> > > > > > Subject: [DynoMotion] AMD 64 on a 32 bit OS
> > > > > >
> > > > > >
> > > > > > ÃÆ'ââ¬Å¡
> > > > > > So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
> > > > > >
> > > > > > I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
> > > > > >
> > > > > > I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
> > > > > >
> > > > > > I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
> > > > > >
> > > > > > I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
> > > > > >
> > > > > > Thanks,
> > > > > > -Brad Murry
> > > > > >
> > > > >
> > > >
> > >
> >
> |
|
| Group: DynoMotion |
Message: 4841 |
From: bradodarb |
Date: 5/8/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Hello Tom,
After a little research, I do not think the modified PID and VID are the issue, I think it is just down to the driver needing to be signed.
-Brad
--- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@...> wrote:
>
>
> Update::
>
> It seems the steps listed do yield a usable system... UNITL you disconnect the Kflop.
>
>
> I may have to look again at those utilities to find a more permanent solution.
>
>
> Tom - how would you like to see this happen to get ready for win8?
>
> -Brad
>
> --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> >
> >
> >
> > Kyryl,
> >
> >
> >
> > You are the man!
> >
> >
> >
> > After a few cycles of downloading the utility from FTDI and running into several dll not found errors- prompting me to try reinstalling the drivers....
> >
> >
> >
> > I received your suggestion and I am now connected to my Kflop inside win8!
> >
> >
> >
> > The actual procedure was simple enough::
> >
> >
> >
> > 1) open msconfig
> >
> > 2) check safe mode from boot tab
> >
> > 3) restart
> >
> > 4) plug in Kflop
> >
> > 5) go to device manager
> >
> > 6) update driver
> >
> > 7) open msconfig
> >
> > 8) reset boot options to the original state
> >
> > 9) restart
> >
> > 10) enjoy kflop on windows 8( and with new kflop web+websocket server create CNC metro app!)
> >
> >
> >
> >
> >
> > Thanks Kyryl for the painless suggestion and Tom for the useful and interesting links.
> >
> >
> >
> > -Brad Murry
> >
> >
> >
> > Sent from my Windows 8 PC
> > --- In DynoMotion@yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > >
> > > As an alternative I would try to disable Driver Signature Enforcement. You will need to enable Safe Mode to do that. Google "Disable Signature Enforcement" "Windows 8".
> > >
> > > -Kyryl
> > >
> > > From: Tom Kerekes
> > > Sent: Friday, May 04, 2012 2:37 PM
> > > To: DynoMotion@yahoogroups.com
> > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > >
> > >
> > >
> > > It is the: FT_PROG 2.6.8 - EEPROM Programming Utility
> > >
> > > TK
> > >
> > >
> > > From: bradodarb <bradodarb@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Friday, May 4, 2012 2:24 PM
> > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > >
> > >
> > >
> > > Hello Tom,
> > >
> > > I'd love to get it working as this box will become my primary dev machine for this kind of stuff and I am really loving Win8.
> > >
> > > So, I'm down to go deep as long as there is a reasonable amount of guidance.
> > >
> > > I looked at the link and noticed many tools, can you specify the correct one?
> > >
> > > If the ID's are the problem. I reckon a new device discovery scheme will need to be thought about so as not to corrupt the expected VID/PID.
> > >
> > > If that is not the issue, I will need to get at that XML.
> > >
> > > Thanks,
> > >
> > > -Brad Murry
> > >
> > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Opps forgot the link to the FT_PROG Utility
> > > > Ã
> > > > http://www.ftdichip.com/Support/Utilities.htm
> > > > Ã
> > > > TK
> > > >
> > > > From: Tom Kerekes <tk@>
> > > > To: "mailto:DynoMotion%40yahoogroups.com" <mailto:DynoMotion%40yahoogroups.com>
> > > > Sent: Friday, May 4, 2012 1:58 PM
> > > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > >
> > > >
> > > > Hi Brad,
> > > > Ã
> > > > I'm not sure how deep you want to get into this but W7 (and I assume W8) includes Microsoft Certified Drivers for the FT245RL USB chip that we use.à However we change the VID and PID to be unique to KFLOP so it can be identified as a KFLOP and not something else with the same FTDI chip.à So Windows thinks the device is incompatible.à There is a utility from FTDI that can be used to erase our Configuration so it will then load the standard Windows supplied drivers.à à You might try that just to see if the device then installs properly into device manager as an FTDI device.à Our libraries only open FTDI devices that contain the word "KFLOP" or "KMotion" or "Dynomotion"à in the driver name so if you do this our Libraries will not recognize the device as a KFLOP.à You might be able to re-name the driver using Device Manager.à Otherwise you could modifyà our KMotionDLL library to attach to any FTDI device by removing the name restriction.à à It's easy
> > > > to re-flash our configuration into the FTDI chip.Ã I'll attach the required XML file in case you don't have it.Ã I wonder if Microsoft in their infinite wisdom now refuses to load non-certified device drivers in W8?
> > > > Ã
> > > > Regards
> > > > TK
> > > >
> > > > From: bradodarb <bradodarb@>
> > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > Sent: Friday, May 4, 2012 1:36 PM
> > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > >
> > > >
> > > > Ã
> > > >
> > > > Thanks Kyryl,
> > > >
> > > > I just installed that driver as well, and no dice I'm afraid.
> > > >
> > > > When I plug the kflop in, I get a notification in my system tray stating that the usb device malfunctioned and widows was unable to recognize it....
> > > >
> > > > Still works on Win7
> > > >
> > > > -Brad Murry
> > > >
> > > > --- In mailto:DynoMotion%40yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > > > >
> > > > > Brad,
> > > > >
> > > > > Have you tried the latest FTDI driver yet? It does not list Win8 as a supported platform, but chances are it may work.
> > > > > http://www.ftdichip.com/Drivers/VCP.htm
> > > > >
> > > > > -Kyryl
> > > > >
> > > > > From: bradodarb
> > > > > Sent: Friday, May 04, 2012 12:01 PM
> > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > >
> > > > >
> > > > > In case anyone is interested in trying this or did not know there was a win8 preview-
> > > > >
> > > > > http://windows.microsoft.com/en-US/windows-8/download
> > > > >
> > > > > I can say that win 8 is amazing so far. from deep hibernate to actually ready to work is less than 4 seconds.
> > > > >
> > > > > Oh well, at least we can get a head start on supporting 8!
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > > --- In mailto:DynoMotion%40yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > > > > >
> > > > > > I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
> > > > > >
> > > > > > I have tried every USB port on this box and it is all the same.
> > > > > >
> > > > > > I plugged it into my dev laptop and it still works, so kflop is good.
> > > > > >
> > > > > > Incidentally, I have several working USB devices on this machine
> > > > > > (mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
> > > > > >
> > > > > > Maybe a win8 bug?
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > >
> > > > > > > Hi Brad,
> > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC.ÃÆ'ââ¬Å¡ If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version.ÃÆ'ââ¬Å¡ So it sounds like your USB connection is not even physically present to get that behavior.ÃÆ'ââ¬Å¡ But yet something appears in device manager?
> > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > Regards
> > > > > > > TK
> > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > ÃÆ'ââ¬Å¡
> > > > > > >
> > > > > > > From: bradodarb <bradodarb@>
> > > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > > Sent: Friday, May 4, 2012 10:30 AM
> > > > > > > Subject: [DynoMotion] AMD 64 on a 32 bit OS
> > > > > > >
> > > > > > >
> > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
> > > > > > >
> > > > > > > I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
> > > > > > >
> > > > > > > I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
> > > > > > >
> > > > > > > I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
> > > > > > >
> > > > > > > I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > -Brad Murry
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> |
|
| Group: DynoMotion |
Message: 4842 |
From: bradodarb |
Date: 5/8/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Hello Tom,
Can you make this happen?
http://technet.microsoft.com/en-us/query/ff544865
Let me know if I can be of any assistance.
-Brad Murry
--- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@...> wrote:
>
> Hello Tom,
>
>
> After a little research, I do not think the modified PID and VID are the issue, I think it is just down to the driver needing to be signed.
>
> -Brad
>
> --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> >
> >
> > Update::
> >
> > It seems the steps listed do yield a usable system... UNITL you disconnect the Kflop.
> >
> >
> > I may have to look again at those utilities to find a more permanent solution.
> >
> >
> > Tom - how would you like to see this happen to get ready for win8?
> >
> > -Brad
> >
> > --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > >
> > >
> > >
> > > Kyryl,
> > >
> > >
> > >
> > > You are the man!
> > >
> > >
> > >
> > > After a few cycles of downloading the utility from FTDI and running into several dll not found errors- prompting me to try reinstalling the drivers....
> > >
> > >
> > >
> > > I received your suggestion and I am now connected to my Kflop inside win8!
> > >
> > >
> > >
> > > The actual procedure was simple enough::
> > >
> > >
> > >
> > > 1) open msconfig
> > >
> > > 2) check safe mode from boot tab
> > >
> > > 3) restart
> > >
> > > 4) plug in Kflop
> > >
> > > 5) go to device manager
> > >
> > > 6) update driver
> > >
> > > 7) open msconfig
> > >
> > > 8) reset boot options to the original state
> > >
> > > 9) restart
> > >
> > > 10) enjoy kflop on windows 8( and with new kflop web+websocket server create CNC metro app!)
> > >
> > >
> > >
> > >
> > >
> > > Thanks Kyryl for the painless suggestion and Tom for the useful and interesting links.
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > Sent from my Windows 8 PC
> > > --- In DynoMotion@yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > > >
> > > > As an alternative I would try to disable Driver Signature Enforcement. You will need to enable Safe Mode to do that. Google "Disable Signature Enforcement" "Windows 8".
> > > >
> > > > -Kyryl
> > > >
> > > > From: Tom Kerekes
> > > > Sent: Friday, May 04, 2012 2:37 PM
> > > > To: DynoMotion@yahoogroups.com
> > > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > >
> > > >
> > > >
> > > > It is the: FT_PROG 2.6.8 - EEPROM Programming Utility
> > > >
> > > > TK
> > > >
> > > >
> > > > From: bradodarb <bradodarb@>
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Friday, May 4, 2012 2:24 PM
> > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > >
> > > >
> > > >
> > > > Hello Tom,
> > > >
> > > > I'd love to get it working as this box will become my primary dev machine for this kind of stuff and I am really loving Win8.
> > > >
> > > > So, I'm down to go deep as long as there is a reasonable amount of guidance.
> > > >
> > > > I looked at the link and noticed many tools, can you specify the correct one?
> > > >
> > > > If the ID's are the problem. I reckon a new device discovery scheme will need to be thought about so as not to corrupt the expected VID/PID.
> > > >
> > > > If that is not the issue, I will need to get at that XML.
> > > >
> > > > Thanks,
> > > >
> > > > -Brad Murry
> > > >
> > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Opps forgot the link to the FT_PROG Utility
> > > > > Ã
> > > > > http://www.ftdichip.com/Support/Utilities.htm
> > > > > Ã
> > > > > TK
> > > > >
> > > > > From: Tom Kerekes <tk@>
> > > > > To: "mailto:DynoMotion%40yahoogroups.com" <mailto:DynoMotion%40yahoogroups.com>
> > > > > Sent: Friday, May 4, 2012 1:58 PM
> > > > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > >
> > > > >
> > > > > Hi Brad,
> > > > > Ã
> > > > > I'm not sure how deep you want to get into this but W7 (and I assume W8) includes Microsoft Certified Drivers for the FT245RL USB chip that we use.à However we change the VID and PID to be unique to KFLOP so it can be identified as a KFLOP and not something else with the same FTDI chip.à So Windows thinks the device is incompatible.à There is a utility from FTDI that can be used to erase our Configuration so it will then load the standard Windows supplied drivers.à à You might try that just to see if the device then installs properly into device manager as an FTDI device.à Our libraries only open FTDI devices that contain the word "KFLOP" or "KMotion" or "Dynomotion"à in the driver name so if you do this our Libraries will not recognize the device as a KFLOP.à You might be able to re-name the driver using Device Manager.à Otherwise you could modifyà our KMotionDLL library to attach to any FTDI device by removing the name restriction.à à It's easy
> > > > > to re-flash our configuration into the FTDI chip.Ã I'll attach the required XML file in case you don't have it.Ã I wonder if Microsoft in their infinite wisdom now refuses to load non-certified device drivers in W8?
> > > > > Ã
> > > > > Regards
> > > > > TK
> > > > >
> > > > > From: bradodarb <bradodarb@>
> > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > Sent: Friday, May 4, 2012 1:36 PM
> > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > >
> > > > >
> > > > > Ã
> > > > >
> > > > > Thanks Kyryl,
> > > > >
> > > > > I just installed that driver as well, and no dice I'm afraid.
> > > > >
> > > > > When I plug the kflop in, I get a notification in my system tray stating that the usb device malfunctioned and widows was unable to recognize it....
> > > > >
> > > > > Still works on Win7
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > > --- In mailto:DynoMotion%40yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > > > > >
> > > > > > Brad,
> > > > > >
> > > > > > Have you tried the latest FTDI driver yet? It does not list Win8 as a supported platform, but chances are it may work.
> > > > > > http://www.ftdichip.com/Drivers/VCP.htm
> > > > > >
> > > > > > -Kyryl
> > > > > >
> > > > > > From: bradodarb
> > > > > > Sent: Friday, May 04, 2012 12:01 PM
> > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > > >
> > > > > >
> > > > > > In case anyone is interested in trying this or did not know there was a win8 preview-
> > > > > >
> > > > > > http://windows.microsoft.com/en-US/windows-8/download
> > > > > >
> > > > > > I can say that win 8 is amazing so far. from deep hibernate to actually ready to work is less than 4 seconds.
> > > > > >
> > > > > > Oh well, at least we can get a head start on supporting 8!
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > > --- In mailto:DynoMotion%40yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > > > > > >
> > > > > > > I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
> > > > > > >
> > > > > > > I have tried every USB port on this box and it is all the same.
> > > > > > >
> > > > > > > I plugged it into my dev laptop and it still works, so kflop is good.
> > > > > > >
> > > > > > > Incidentally, I have several working USB devices on this machine
> > > > > > > (mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
> > > > > > >
> > > > > > > Maybe a win8 bug?
> > > > > > >
> > > > > > > -Brad Murry
> > > > > > >
> > > > > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > > >
> > > > > > > > Hi Brad,
> > > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > > The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC.ÃÆ'ââ¬Å¡ If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version.ÃÆ'ââ¬Å¡ So it sounds like your USB connection is not even physically present to get that behavior.ÃÆ'ââ¬Å¡ But yet something appears in device manager?
> > > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > > Regards
> > > > > > > > TK
> > > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > >
> > > > > > > > From: bradodarb <bradodarb@>
> > > > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > > > Sent: Friday, May 4, 2012 10:30 AM
> > > > > > > > Subject: [DynoMotion] AMD 64 on a 32 bit OS
> > > > > > > >
> > > > > > > >
> > > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > > So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
> > > > > > > >
> > > > > > > > I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
> > > > > > > >
> > > > > > > > I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
> > > > > > > >
> > > > > > > > I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
> > > > > > > >
> > > > > > > > I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > -Brad Murry
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> |
|
| Group: DynoMotion |
Message: 4843 |
From: bradodarb |
Date: 5/8/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Hello Tom,
Can you make this happen?
http://technet.microsoft.com/en-us/query/ff544865
Let me know if I can be of any assistance.
-Brad Murry
--- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@...> wrote:
>
> Hello Tom,
>
>
> After a little research, I do not think the modified PID and VID are the issue, I think it is just down to the driver needing to be signed.
>
> -Brad
>
> --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> >
> >
> > Update::
> >
> > It seems the steps listed do yield a usable system... UNITL you disconnect the Kflop.
> >
> >
> > I may have to look again at those utilities to find a more permanent solution.
> >
> >
> > Tom - how would you like to see this happen to get ready for win8?
> >
> > -Brad
> >
> > --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > >
> > >
> > >
> > > Kyryl,
> > >
> > >
> > >
> > > You are the man!
> > >
> > >
> > >
> > > After a few cycles of downloading the utility from FTDI and running into several dll not found errors- prompting me to try reinstalling the drivers....
> > >
> > >
> > >
> > > I received your suggestion and I am now connected to my Kflop inside win8!
> > >
> > >
> > >
> > > The actual procedure was simple enough::
> > >
> > >
> > >
> > > 1) open msconfig
> > >
> > > 2) check safe mode from boot tab
> > >
> > > 3) restart
> > >
> > > 4) plug in Kflop
> > >
> > > 5) go to device manager
> > >
> > > 6) update driver
> > >
> > > 7) open msconfig
> > >
> > > 8) reset boot options to the original state
> > >
> > > 9) restart
> > >
> > > 10) enjoy kflop on windows 8( and with new kflop web+websocket server create CNC metro app!)
> > >
> > >
> > >
> > >
> > >
> > > Thanks Kyryl for the painless suggestion and Tom for the useful and interesting links.
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > Sent from my Windows 8 PC
> > > --- In DynoMotion@yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > > >
> > > > As an alternative I would try to disable Driver Signature Enforcement. You will need to enable Safe Mode to do that. Google "Disable Signature Enforcement" "Windows 8".
> > > >
> > > > -Kyryl
> > > >
> > > > From: Tom Kerekes
> > > > Sent: Friday, May 04, 2012 2:37 PM
> > > > To: DynoMotion@yahoogroups.com
> > > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > >
> > > >
> > > >
> > > > It is the: FT_PROG 2.6.8 - EEPROM Programming Utility
> > > >
> > > > TK
> > > >
> > > >
> > > > From: bradodarb <bradodarb@>
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Friday, May 4, 2012 2:24 PM
> > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > >
> > > >
> > > >
> > > > Hello Tom,
> > > >
> > > > I'd love to get it working as this box will become my primary dev machine for this kind of stuff and I am really loving Win8.
> > > >
> > > > So, I'm down to go deep as long as there is a reasonable amount of guidance.
> > > >
> > > > I looked at the link and noticed many tools, can you specify the correct one?
> > > >
> > > > If the ID's are the problem. I reckon a new device discovery scheme will need to be thought about so as not to corrupt the expected VID/PID.
> > > >
> > > > If that is not the issue, I will need to get at that XML.
> > > >
> > > > Thanks,
> > > >
> > > > -Brad Murry
> > > >
> > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Opps forgot the link to the FT_PROG Utility
> > > > > Ã
> > > > > http://www.ftdichip.com/Support/Utilities.htm
> > > > > Ã
> > > > > TK
> > > > >
> > > > > From: Tom Kerekes <tk@>
> > > > > To: "mailto:DynoMotion%40yahoogroups.com" <mailto:DynoMotion%40yahoogroups.com>
> > > > > Sent: Friday, May 4, 2012 1:58 PM
> > > > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > >
> > > > >
> > > > > Hi Brad,
> > > > > Ã
> > > > > I'm not sure how deep you want to get into this but W7 (and I assume W8) includes Microsoft Certified Drivers for the FT245RL USB chip that we use.à However we change the VID and PID to be unique to KFLOP so it can be identified as a KFLOP and not something else with the same FTDI chip.à So Windows thinks the device is incompatible.à There is a utility from FTDI that can be used to erase our Configuration so it will then load the standard Windows supplied drivers.à à You might try that just to see if the device then installs properly into device manager as an FTDI device.à Our libraries only open FTDI devices that contain the word "KFLOP" or "KMotion" or "Dynomotion"à in the driver name so if you do this our Libraries will not recognize the device as a KFLOP.à You might be able to re-name the driver using Device Manager.à Otherwise you could modifyà our KMotionDLL library to attach to any FTDI device by removing the name restriction.à à It's easy
> > > > > to re-flash our configuration into the FTDI chip.Ã I'll attach the required XML file in case you don't have it.Ã I wonder if Microsoft in their infinite wisdom now refuses to load non-certified device drivers in W8?
> > > > > Ã
> > > > > Regards
> > > > > TK
> > > > >
> > > > > From: bradodarb <bradodarb@>
> > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > Sent: Friday, May 4, 2012 1:36 PM
> > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > >
> > > > >
> > > > > Ã
> > > > >
> > > > > Thanks Kyryl,
> > > > >
> > > > > I just installed that driver as well, and no dice I'm afraid.
> > > > >
> > > > > When I plug the kflop in, I get a notification in my system tray stating that the usb device malfunctioned and widows was unable to recognize it....
> > > > >
> > > > > Still works on Win7
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > > --- In mailto:DynoMotion%40yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > > > > >
> > > > > > Brad,
> > > > > >
> > > > > > Have you tried the latest FTDI driver yet? It does not list Win8 as a supported platform, but chances are it may work.
> > > > > > http://www.ftdichip.com/Drivers/VCP.htm
> > > > > >
> > > > > > -Kyryl
> > > > > >
> > > > > > From: bradodarb
> > > > > > Sent: Friday, May 04, 2012 12:01 PM
> > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > > >
> > > > > >
> > > > > > In case anyone is interested in trying this or did not know there was a win8 preview-
> > > > > >
> > > > > > http://windows.microsoft.com/en-US/windows-8/download
> > > > > >
> > > > > > I can say that win 8 is amazing so far. from deep hibernate to actually ready to work is less than 4 seconds.
> > > > > >
> > > > > > Oh well, at least we can get a head start on supporting 8!
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > > --- In mailto:DynoMotion%40yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > > > > > >
> > > > > > > I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
> > > > > > >
> > > > > > > I have tried every USB port on this box and it is all the same.
> > > > > > >
> > > > > > > I plugged it into my dev laptop and it still works, so kflop is good.
> > > > > > >
> > > > > > > Incidentally, I have several working USB devices on this machine
> > > > > > > (mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
> > > > > > >
> > > > > > > Maybe a win8 bug?
> > > > > > >
> > > > > > > -Brad Murry
> > > > > > >
> > > > > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > > >
> > > > > > > > Hi Brad,
> > > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > > The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC.ÃÆ'ââ¬Å¡ If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version.ÃÆ'ââ¬Å¡ So it sounds like your USB connection is not even physically present to get that behavior.ÃÆ'ââ¬Å¡ But yet something appears in device manager?
> > > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > > Regards
> > > > > > > > TK
> > > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > >
> > > > > > > > From: bradodarb <bradodarb@>
> > > > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > > > Sent: Friday, May 4, 2012 10:30 AM
> > > > > > > > Subject: [DynoMotion] AMD 64 on a 32 bit OS
> > > > > > > >
> > > > > > > >
> > > > > > > > ÃÆ'ââ¬Å¡
> > > > > > > > So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
> > > > > > > >
> > > > > > > > I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
> > > > > > > >
> > > > > > > > I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
> > > > > > > >
> > > > > > > > I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
> > > > > > > >
> > > > > > > > I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > -Brad Murry
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> |
|
| Group: DynoMotion |
Message: 4851 |
From: Tom Kerekes |
Date: 5/8/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Hi Brad,
I did load the W8 preview on my VIAO dual core laptop and it runs, but haven't had time to experiment yet.
Yeah you could explain what we need to do :}
All we really do is take the USB Driver files from FTDI (which are actually MS Certified) and make a new .inf file to install them. They actually provide a utility to help with this. MS then declares those to be the un-certified.
Regards
TK
| Group: DynoMotion |
Message: 4863 |
From: Tom Kerekes |
Date: 5/8/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Hi Brad,
BTW I upgraded a W7 system with KFLOP already installed to W8 and it seems to work fine.
Under Device Manager under the Device Properties for Digital Signer it says Not Digitally Signed.
Regards
TK
| Group: DynoMotion |
Message: 4876 |
From: bradodarb |
Date: 5/9/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Hello Tom,
My system was a fresh install from USB boot.
Sounds like a nice methodology is built in to 'grandfather in' unsigned drivers that existed on the system prior to upgrade.
-Brad Murry
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Brad,
> Â
> BTW I upgraded a W7 system with KFLOP already installed to W8 and it seems to work fine.
> Â
> Under Device Manager under the Device Properties for Digital Signer it says Not Digitally Signed.
> Â
> Regards
> TK
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, May 8, 2012 10:20 AM
> Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
>
>
> Â
> Hello Tom,
>
> Can you make this happen?
>
> http://technet.microsoft.com/en-us/query/ff544865
>
> Let me know if I can be of any assistance.
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> >
> > Hello Tom,
> >
> >
> > After a little research, I do not think the modified PID and VID are the issue, I think it is just down to the driver needing to be signed.
> >
> > -Brad
> >
> > --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > >
> > >
> > > Update::
> > >
> > > It seems the steps listed do yield a usable system... UNITL you disconnect the Kflop.
> > >
> > >
> > > I may have to look again at those utilities to find a more permanent solution.
> > >
> > >
> > > Tom - how would you like to see this happen to get ready for win8?
> > >
> > > -Brad
> > >
> > > --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > > >
> > > >
> > > >
> > > > Kyryl,
> > > >
> > > >
> > > >
> > > > You are the man!
> > > >
> > > >
> > > >
> > > > After a few cycles of downloading the utility from FTDI and running into several dll not found errors- prompting me to try reinstalling the drivers....
> > > >
> > > >
> > > >
> > > > I received your suggestion and I am now connected to my Kflop inside win8!
> > > >
> > > >
> > > >
> > > > The actual procedure was simple enough::
> > > >
> > > >
> > > >
> > > > 1) open msconfig
> > > >
> > > > 2) check safe mode from boot tab
> > > >
> > > > 3) restart
> > > >
> > > > 4) plug in Kflop
> > > >
> > > > 5) go to device manager
> > > >
> > > > 6) update driver
> > > >
> > > > 7) open msconfig
> > > >
> > > > 8) reset boot options to the original state
> > > >
> > > > 9) restart
> > > >
> > > > 10) enjoy kflop on windows 8( and with new kflop web+websocket server create CNC metro app!)
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Thanks Kyryl for the painless suggestion and Tom for the useful and interesting links.
> > > >
> > > >
> > > >
> > > > -Brad Murry
> > > >
> > > >
> > > >
> > > > Sent from my Windows 8 PC
> > > > --- In DynoMotion@yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > > > >
> > > > > As an alternative I would try to disable Driver Signature Enforcement. You will need to enable Safe Mode to do that. Google "Disable Signature Enforcement" "Windows 8".
> > > > >
> > > > > -Kyryl
> > > > >
> > > > > From: Tom Kerekes
> > > > > Sent: Friday, May 04, 2012 2:37 PM
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > >
> > > > >
> > > > >
> > > > > It is the: FT_PROG 2.6.8 - EEPROM Programming Utility
> > > > >
> > > > > TK
> > > > >
> > > > >
> > > > > From: bradodarb <bradodarb@>
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Friday, May 4, 2012 2:24 PM
> > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > >
> > > > >
> > > > >
> > > > > Hello Tom,
> > > > >
> > > > > I'd love to get it working as this box will become my primary dev machine for this kind of stuff and I am really loving Win8.
> > > > >
> > > > > So, I'm down to go deep as long as there is a reasonable amount of guidance.
> > > > >
> > > > > I looked at the link and noticed many tools, can you specify the correct one?
> > > > >
> > > > > If the ID's are the problem. I reckon a new device discovery scheme will need to be thought about so as not to corrupt the expected VID/PID.
> > > > >
> > > > > If that is not the issue, I will need to get at that XML.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > >
> > > > > > Opps forgot the link to the FT_PROG Utility
> > > > > > Ãâ
> > > > > > http://www.ftdichip.com/Support/Utilities.htm
> > > > > > Ãâ
> > > > > > TK
> > > > > >
> > > > > > From: Tom Kerekes <tk@>
> > > > > > To: "mailto:DynoMotion%40yahoogroups.com" <mailto:DynoMotion%40yahoogroups.com>
> > > > > > Sent: Friday, May 4, 2012 1:58 PM
> > > > > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > > >
> > > > > >
> > > > > > Hi Brad,
> > > > > > Ãâ
> > > > > > I'm not sure how deep you want to get into this but W7 (and I assume W8) includes Microsoft Certified Drivers for the FT245RL USB chip that we use.Ãâ However we change the VID and PID to be unique to KFLOP so it can be identified as a KFLOP and not something else with the same FTDI chip.Ãâ So Windows thinks the device is incompatible.Ãâ There is a utility from FTDI that can be used to erase our Configuration so it will then load the standard Windows supplied drivers.Ãâ Ãâ You might try that just to see if the device then installs properly into device manager as an FTDI device.Ãâ Our libraries only open FTDI devices that contain the word "KFLOP" or "KMotion" or "Dynomotion"Ãâ in the driver name so if you do this our Libraries will not recognize the device as a KFLOP.Ãâ You might be able to re-name the driver using Device Manager.Ãâ Otherwise you could modifyÃâ our KMotionDLL library to attach to any FTDI device by
> removing the name restriction.Ãâ Ãâ It's easy
> > > > > > to re-flash our configuration into the FTDI chip.Ãâ I'll attach the required XML file in case you don't have it.Ãâ I wonder if Microsoft in their infinite wisdom now refuses to load non-certified device drivers in W8?
> > > > > > Ãâ
> > > > > > Regards
> > > > > > TK
> > > > > >
> > > > > > From: bradodarb <bradodarb@>
> > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > Sent: Friday, May 4, 2012 1:36 PM
> > > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > > >
> > > > > >
> > > > > > Ãâ
> > > > > >
> > > > > > Thanks Kyryl,
> > > > > >
> > > > > > I just installed that driver as well, and no dice I'm afraid.
> > > > > >
> > > > > > When I plug the kflop in, I get a notification in my system tray stating that the usb device malfunctioned and widows was unable to recognize it....
> > > > > >
> > > > > > Still works on Win7
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > > --- In mailto:DynoMotion%40yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > > > > > >
> > > > > > > Brad,
> > > > > > >
> > > > > > > Have you tried the latest FTDI driver yet? It does not list Win8 as a supported platform, but chances are it may work.
> > > > > > > http://www.ftdichip.com/Drivers/VCP.htm
> > > > > > >
> > > > > > > -Kyryl
> > > > > > >
> > > > > > > From: bradodarb
> > > > > > > Sent: Friday, May 04, 2012 12:01 PM
> > > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > > > >
> > > > > > >
> > > > > > > In case anyone is interested in trying this or did not know there was a win8 preview-
> > > > > > >
> > > > > > > http://windows.microsoft.com/en-US/windows-8/download
> > > > > > >
> > > > > > > I can say that win 8 is amazing so far. from deep hibernate to actually ready to work is less than 4 seconds.
> > > > > > >
> > > > > > > Oh well, at least we can get a head start on supporting 8!
> > > > > > >
> > > > > > > -Brad Murry
> > > > > > >
> > > > > > > --- In mailto:DynoMotion%40yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > > > > > > >
> > > > > > > > I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
> > > > > > > >
> > > > > > > > I have tried every USB port on this box and it is all the same.
> > > > > > > >
> > > > > > > > I plugged it into my dev laptop and it still works, so kflop is good.
> > > > > > > >
> > > > > > > > Incidentally, I have several working USB devices on this machine
> > > > > > > > (mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
> > > > > > > >
> > > > > > > > Maybe a win8 bug?
> > > > > > > >
> > > > > > > > -Brad Murry
> > > > > > > >
> > > > > > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > > > >
> > > > > > > > > Hi Brad,
> > > > > > > > > ÃÆ'Ã'âââ¬Ã
¡
> > > > > > > > > The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC.ÃÆ'Ã'âââ¬Ã
¡ If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version.ÃÆ'Ã'âââ¬Ã
¡ So it sounds like your USB connection is not even physically present to get that behavior.ÃÆ'Ã'âââ¬Ã
¡ But yet something appears in device manager?
> > > > > > > > > ÃÆ'Ã'âââ¬Ã
¡
> > > > > > > > > Regards
> > > > > > > > > TK
> > > > > > > > > ÃÆ'Ã'âââ¬Ã
¡
> > > > > > > > > ÃÆ'Ã'âââ¬Ã
¡
> > > > > > > > >
> > > > > > > > > From: bradodarb <bradodarb@>
> > > > > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > > > > Sent: Friday, May 4, 2012 10:30 AM
> > > > > > > > > Subject: [DynoMotion] AMD 64 on a 32 bit OS
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ÃÆ'Ã'âââ¬Ã
¡
> > > > > > > > > So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
> > > > > > > > >
> > > > > > > > > I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
> > > > > > > > >
> > > > > > > > > I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
> > > > > > > > >
> > > > > > > > > I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
> > > > > > > > >
> > > > > > > > > I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > -Brad Murry
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> |
|
| Group: DynoMotion |
Message: 4877 |
From: bradodarb |
Date: 5/9/2012 |
| Subject: Re: AMD 64 on a 32 bit OS |
Hello Tom,
Also, even on Win7 you need to jump through some hoops to get the driver installed(admin rights + manual driver install with lots of warnings).
I'm pretty sure signing the driver will eliminate that whole side of it.
An overview is here::
http://technet.microsoft.com/en-us/query/ff549724
And the process is fairly well defined here::
http://msdn.microsoft.com/en-us/windows/hardware/gg487332.aspx
Looks like the first step is to obtain a valid certificate from a third party.
-Brad Murry
--- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@...> wrote:
>
> Hello Tom,
>
> My system was a fresh install from USB boot.
>
> Sounds like a nice methodology is built in to 'grandfather in' unsigned drivers that existed on the system prior to upgrade.
>
> -Brad Murry
>
>
>
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Brad,
> > Â
> > BTW I upgraded a W7 system with KFLOP already installed to W8 and it seems to work fine.
> > Â
> > Under Device Manager under the Device Properties for Digital Signer it says Not Digitally Signed.
> > Â
> > Regards
> > TK
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, May 8, 2012 10:20 AM
> > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> >
> >
> > Â
> > Hello Tom,
> >
> > Can you make this happen?
> >
> > http://technet.microsoft.com/en-us/query/ff544865
> >
> > Let me know if I can be of any assistance.
> >
> > -Brad Murry
> >
> > --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > >
> > > Hello Tom,
> > >
> > >
> > > After a little research, I do not think the modified PID and VID are the issue, I think it is just down to the driver needing to be signed.
> > >
> > > -Brad
> > >
> > > --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > > >
> > > >
> > > > Update::
> > > >
> > > > It seems the steps listed do yield a usable system... UNITL you disconnect the Kflop.
> > > >
> > > >
> > > > I may have to look again at those utilities to find a more permanent solution.
> > > >
> > > >
> > > > Tom - how would you like to see this happen to get ready for win8?
> > > >
> > > > -Brad
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > > > >
> > > > >
> > > > >
> > > > > Kyryl,
> > > > >
> > > > >
> > > > >
> > > > > You are the man!
> > > > >
> > > > >
> > > > >
> > > > > After a few cycles of downloading the utility from FTDI and running into several dll not found errors- prompting me to try reinstalling the drivers....
> > > > >
> > > > >
> > > > >
> > > > > I received your suggestion and I am now connected to my Kflop inside win8!
> > > > >
> > > > >
> > > > >
> > > > > The actual procedure was simple enough::
> > > > >
> > > > >
> > > > >
> > > > > 1) open msconfig
> > > > >
> > > > > 2) check safe mode from boot tab
> > > > >
> > > > > 3) restart
> > > > >
> > > > > 4) plug in Kflop
> > > > >
> > > > > 5) go to device manager
> > > > >
> > > > > 6) update driver
> > > > >
> > > > > 7) open msconfig
> > > > >
> > > > > 8) reset boot options to the original state
> > > > >
> > > > > 9) restart
> > > > >
> > > > > 10) enjoy kflop on windows 8( and with new kflop web+websocket server create CNC metro app!)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Thanks Kyryl for the painless suggestion and Tom for the useful and interesting links.
> > > > >
> > > > >
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > >
> > > > >
> > > > > Sent from my Windows 8 PC
> > > > > --- In DynoMotion@yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > > > > >
> > > > > > As an alternative I would try to disable Driver Signature Enforcement. You will need to enable Safe Mode to do that. Google "Disable Signature Enforcement" "Windows 8".
> > > > > >
> > > > > > -Kyryl
> > > > > >
> > > > > > From: Tom Kerekes
> > > > > > Sent: Friday, May 04, 2012 2:37 PM
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > > >
> > > > > >
> > > > > >
> > > > > > It is the: FT_PROG 2.6.8 - EEPROM Programming Utility
> > > > > >
> > > > > > TK
> > > > > >
> > > > > >
> > > > > > From: bradodarb <bradodarb@>
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Friday, May 4, 2012 2:24 PM
> > > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hello Tom,
> > > > > >
> > > > > > I'd love to get it working as this box will become my primary dev machine for this kind of stuff and I am really loving Win8.
> > > > > >
> > > > > > So, I'm down to go deep as long as there is a reasonable amount of guidance.
> > > > > >
> > > > > > I looked at the link and noticed many tools, can you specify the correct one?
> > > > > >
> > > > > > If the ID's are the problem. I reckon a new device discovery scheme will need to be thought about so as not to corrupt the expected VID/PID.
> > > > > >
> > > > > > If that is not the issue, I will need to get at that XML.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > >
> > > > > > > Opps forgot the link to the FT_PROG Utility
> > > > > > > Ãâ
> > > > > > > http://www.ftdichip.com/Support/Utilities.htm
> > > > > > > Ãâ
> > > > > > > TK
> > > > > > >
> > > > > > > From: Tom Kerekes <tk@>
> > > > > > > To: "mailto:DynoMotion%40yahoogroups.com" <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > Sent: Friday, May 4, 2012 1:58 PM
> > > > > > > Subject: Re: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > > > >
> > > > > > >
> > > > > > > Hi Brad,
> > > > > > > Ãâ
> > > > > > > I'm not sure how deep you want to get into this but W7 (and I assume W8) includes Microsoft Certified Drivers for the FT245RL USB chip that we use.Ãâ However we change the VID and PID to be unique to KFLOP so it can be identified as a KFLOP and not something else with the same FTDI chip.Ãâ So Windows thinks the device is incompatible.Ãâ There is a utility from FTDI that can be used to erase our Configuration so it will then load the standard Windows supplied drivers.Ãâ Ãâ You might try that just to see if the device then installs properly into device manager as an FTDI device.Ãâ Our libraries only open FTDI devices that contain the word "KFLOP" or "KMotion" or "Dynomotion"Ãâ in the driver name so if you do this our Libraries will not recognize the device as a KFLOP.Ãâ You might be able to re-name the driver using Device Manager.Ãâ Otherwise you could modifyÃâ our KMotionDLL library to attach to any FTDI device by
> > removing the name restriction.Ãâ Ãâ It's easy
> > > > > > > to re-flash our configuration into the FTDI chip.Ãâ I'll attach the required XML file in case you don't have it.Ãâ I wonder if Microsoft in their infinite wisdom now refuses to load non-certified device drivers in W8?
> > > > > > > Ãâ
> > > > > > > Regards
> > > > > > > TK
> > > > > > >
> > > > > > > From: bradodarb <bradodarb@>
> > > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > > Sent: Friday, May 4, 2012 1:36 PM
> > > > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > > > >
> > > > > > >
> > > > > > > Ãâ
> > > > > > >
> > > > > > > Thanks Kyryl,
> > > > > > >
> > > > > > > I just installed that driver as well, and no dice I'm afraid.
> > > > > > >
> > > > > > > When I plug the kflop in, I get a notification in my system tray stating that the usb device malfunctioned and widows was unable to recognize it....
> > > > > > >
> > > > > > > Still works on Win7
> > > > > > >
> > > > > > > -Brad Murry
> > > > > > >
> > > > > > > --- In mailto:DynoMotion%40yahoogroups.com, "Kyryl Perederiy" <kyrylo@> wrote:
> > > > > > > >
> > > > > > > > Brad,
> > > > > > > >
> > > > > > > > Have you tried the latest FTDI driver yet? It does not list Win8 as a supported platform, but chances are it may work.
> > > > > > > > http://www.ftdichip.com/Drivers/VCP.htm
> > > > > > > >
> > > > > > > > -Kyryl
> > > > > > > >
> > > > > > > > From: bradodarb
> > > > > > > > Sent: Friday, May 04, 2012 12:01 PM
> > > > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > > > Subject: [DynoMotion] Re: AMD 64 on a 32 bit OS
> > > > > > > >
> > > > > > > >
> > > > > > > > In case anyone is interested in trying this or did not know there was a win8 preview-
> > > > > > > >
> > > > > > > > http://windows.microsoft.com/en-US/windows-8/download
> > > > > > > >
> > > > > > > > I can say that win 8 is amazing so far. from deep hibernate to actually ready to work is less than 4 seconds.
> > > > > > > >
> > > > > > > > Oh well, at least we can get a head start on supporting 8!
> > > > > > > >
> > > > > > > > -Brad Murry
> > > > > > > >
> > > > > > > > --- In mailto:DynoMotion%40yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > > > > > > > >
> > > > > > > > > I verified it is in the Device Manager under [Other Devices] listed as ! Unknown device
> > > > > > > > >
> > > > > > > > > I have tried every USB port on this box and it is all the same.
> > > > > > > > >
> > > > > > > > > I plugged it into my dev laptop and it still works, so kflop is good.
> > > > > > > > >
> > > > > > > > > Incidentally, I have several working USB devices on this machine
> > > > > > > > > (mouse, keyboard, webcam, Skype headset and I have also been able to USB connect to several other micro-controllers with no probs.
> > > > > > > > >
> > > > > > > > > Maybe a win8 bug?
> > > > > > > > >
> > > > > > > > > -Brad Murry
> > > > > > > > >
> > > > > > > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Brad,
> > > > > > > > > > ÃÆ'Ã'âââ¬Ã
¡
> > > > > > > > > > The 3 seconds of rapid blinking that KFLOP normally does is performed by the bootloader to check if a Flash recovery is being requested by the PC.ÃÆ'Ã'âââ¬Ã
¡ If KFLOP determines that there is no PC connection (by checking the +5V line on the USB connector) it skips that and jumps immediately into the Firmware Version.ÃÆ'Ã'âââ¬Ã
¡ So it sounds like your USB connection is not even physically present to get that behavior.ÃÆ'Ã'âââ¬Ã
¡ But yet something appears in device manager?
> > > > > > > > > > ÃÆ'Ã'âââ¬Ã
¡
> > > > > > > > > > Regards
> > > > > > > > > > TK
> > > > > > > > > > ÃÆ'Ã'âââ¬Ã
¡
> > > > > > > > > > ÃÆ'Ã'âââ¬Ã
¡
> > > > > > > > > >
> > > > > > > > > > From: bradodarb <bradodarb@>
> > > > > > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > > > > > Sent: Friday, May 4, 2012 10:30 AM
> > > > > > > > > > Subject: [DynoMotion] AMD 64 on a 32 bit OS
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ÃÆ'Ã'âââ¬Ã
¡
> > > > > > > > > > So I re-commissioned a ~3 year old optiplex740 with an AMD64bit proc.
> > > > > > > > > >
> > > > > > > > > > I am running Windows8 32 bit because the 64bit version did not support drivers for my NVidia Quattro.
> > > > > > > > > >
> > > > > > > > > > I was able to install KMotion4.29 with no real issues, but when I plug in my kflop, I don't get the normal blinking pattern, just a quick single pulse and then both on solid.
> > > > > > > > > >
> > > > > > > > > > I also cannot seem to install the FTDI driver. It just shows up as unknown device in the device manager and when I try to manually install the driver it states there is no suitable driver found.
> > > > > > > > > >
> > > > > > > > > > I know Win8 is not supported yet by Dyno, but I'm hoping someone can offer some suggestions.
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > -Brad Murry
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> |
|
| | | | | | | | | | | | | |
